-
Notifications
You must be signed in to change notification settings - Fork 10
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
GEN-764 | Catch errors in debug dialog shortcut effect #2795
GEN-764 | Catch errors in debug dialog shortcut effect #2795
Conversation
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
Current dependencies on/for this PR: This comment was auto-generated by Graphite. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Do you think we need it? Datadog should log unhandled errors as it is. Are we expecting anything else than programming errors here?
I think we are expecting some browsers to not support the APIs we are using The reason to log it to Datadog is to add the context of which type of event we are dealing with etc. But perhaps it's not such a big concern to just log as exception |
cd15483
to
8dd8735
Compare
8dd8735
to
19c91c8
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Discussed in person, looks good
Describe your changes
Avoid error when checking shortcut for debug dialog
Source: https://datadoghq.eu/rum/[email protected]:d86e86d8-8d9a-4b00-a2cb-10b8d7671fa2&issueId=00c44958-2246-11ee-83d3-da7ad0900005&from_ts=1689590266557&to_ts=1689593866557&live=true
Justify why they are needed
We don't want uncaught exceptions
I decided to log an error if the code would still contain some issues
Checklist before requesting a review